Skip to content

feat(gateway): expose agent semantic projections - #270

Merged
AntoineToussaint merged 1 commit into
mainfrom
fix/gateway-semantic-index
Aug 9, 2026
Merged

feat(gateway): expose agent semantic projections#270
AntoineToussaint merged 1 commit into
mainfrom
fix/gateway-semantic-index

Conversation

@AntoineToussaint

Copy link
Copy Markdown
Contributor

Closes #268.

What changed

  • add the Tooling client to supervised production-agent sessions
  • route one exact CodeUnitTarget through Gateway GetSemanticIndex
  • rebase every body-free file, symbol-use, and issue location into repository coordinates
  • preserve typed analyzer state, provenance, issues, and failures without language selection in the Gateway
  • pin the released semantic-capable Go, Python, generic, Next.js, Rust, and Swift agents

Verification

  • GOWORK=off go test ./... -count=1
  • real JVM and .NET code-unit projection through released generic agent v0.0.19
  • full Gateway integrations through released Python v0.0.29 and Next.js v0.0.132

@AntoineToussaint
AntoineToussaint force-pushed the fix/gateway-semantic-index branch from be160e8 to a001e34 Compare August 9, 2026 01:06
@AntoineToussaint
AntoineToussaint merged commit f162b30 into main Aug 9, 2026
5 checks passed
@AntoineToussaint
AntoineToussaint deleted the fix/gateway-semantic-index branch August 9, 2026 01:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Expose per-code-unit semantic projection through the Gateway

1 participant